Temenos Lifecycle Management Suite - Recovery Product Guide
Promise to Pay Workflow Step

The Promise to Pay workflow step is used to record promises on account(s) in context for the workflow. In addition to generating a promise to pay on one account, promises can be generated on multiple accounts, or on a person as a whole, as long as the promise step is included in a multi-account workflow.

Running the Promise to Pay Workflow Step

Navigate to the Workflows menu in the Left Navigation Panel, and click the Promise to Pay workflow that was created by the administrator.

If running a multi-account promise to pay workflow, the Select Items pop-up window appears. Select the accounts to be included in the workflow. By default, the account that is open in the workspace is automatically selected. The accounts in this window are available to make promise arrangements.

The Select Items pop-up window contains the Related Accounts grid. The Related Accounts grid must be configured to display somewhere on the workspace in order for the multi-account workflow to work correctly.

Once all accounts are selected, click OK to continue to the Promise to Pay workflow.

There can be only one open promise on an account at a time. If there is already an open or pending promise on an account, the workflow prompts to cancel the open promise in order to create a new one.

The Promise to Pay step appears in the workspace with two sections: Accounts and Payments.

The Accounts section displays the account for which the user is making a promise. From here, users can set the Promise Amount, Number of Payments, Payment Method, Frequency, First Payment, and Tolerance %.

Details of each field are included below:

ShowField Details

Column Description Picture
Promise Amount To set the Promise Amount, click within the Promise Amount column and enter the total promise amount for that account.
The minimum promise value % of the total DQ amount is determined by the system administrator in System Management > Users > Collection Settings. If the promise amount has been set too high based on this setting, a message is received upon clicking Go to Next Step in the workflow that the promise requires approval.
Number of Payments To set the number of payments, click within the Number of Payments column. Click the drop down and select the number of payments that are to be made towards the promise amount.
The maximum amount of promise payments is determined by the system administrator in System Management > Users > Collection Settings.
Payment Method To set the Payment Method, click within the Payment Method column. Click the drop down and select the method of payment for the promise. The payment method drop down is set in System Management >Payment Types.
Administrators have the ability to assign “Delays” to payment methods. For example, if an administrator assigns a promise delay of 2 days to the Check payment type, a promise payment is not considered broken until after the supplied number of days following the promise due date. The delay value is also used to set the Next Contact Date automatically when a promise payment is created or edited. This is set in System Management >Payment Types.
Frequency To set the Payment Frequency, click within the Payment Frequency drop down column. Click the drop down to select the frequency.
First Payment Determine the first payment date by clicking in the First Payment column. Click the calendar icon and select the first payment date.
Tolerance % Users can set a Tolerance percentage on the total DQ amount to allow the account holder to not pay the full delinquent amount to be considered current. Click in the column and select a tolerance percentage to apply to the total DQ Amount. The values in the drop-down represent percentages of the total DQ amount that disperse among the scheduled payments when applied.
The Tolerance % drop-down is a global setting set by an administrator on the Promise Settings tab in System Management > Modules > Collection.

When finished customizing the promise to pay details, click Generate Payments at the top of the Accounts section. Based on the selections, the system generates the list of payments in the Payments section of the workflow step.

The following columns display in this section: 

Column Name Description
Account Displays the account to which the promise to pay is being applied.
Due Date Displays the Due date of each payment.
Amount Displays the amount that is owed to satisfy the promise.
Type Displays the payment type for the promise.

As shown above, a promise value of $1,235.73 was made, with the number of payments set to 5. The payment method was set to check, the frequency to monthly and the initial due date to XX/XX/XXXX. The system calculates the amount of payments and provides all of the payment information for the promise in the section.

ShowAdding a Payment

Individual payments can be added within the Payments section by clicking the Add Payment button. Clicking this option opens a pop-up. Select the account to apply the promise to, the due date, amount of the payment, and the payment type and click Create. The new payment populates in the Payments list and the Accounts section of the workflow step is automatically updated to include the new payment information.

ShowEditing a Payment

Individual payments’ due dates, amounts, and the type can be edited manually by clicking in the respective column in the Payments section. If the changes exceed the limitations set by the system administrator, an approval confirmation appears and the next step in the workflow is assigned to a user to approve the changes on the promise.

ShowRemoving a Payment

To remove a payment from this section, highlight a payment and click Remove Payment. The following message appears stating that when an individual promise payment is removed or cancelled, the total promise amount is updated. Click OK. The changes made are automatically updated within the Accounts section of the workflow step.

When finished entering all payment information, click Go To Next Step to complete the workflow step. If configured, the Next Contact date adjusts to correspond to the promise due date.

Configuring the Next Contact Date is at the discretion of the system administrator. The following options are available to set when a promise is created/edited:

  • Always adjust NCD: Next Contact Date automatically updates to correspond with the promise payment due dates.
  • Prompt to Adjust NCD: The user is prompted to decide whether to adjust the Next Contact Date to correspond with the payment due dates or keep the original Next Contact Date.
  • Do Not Adjust NCD: The Next Contact Date is not affected by promise payment dates.

In addition to the above options, system administrators can also configure a setting that automatically advances the Next Contact Date calculated for a promise by one day.

For more information, please see the Promise Settings Tab section of the Collection topic in the Administrator Guide.

When the promise is submitted, it is documented in the Promise History screen. Please see the Promise History Screen topic for more information.

See Also

Person System Screens

Account Servicing

Solutions

 

 


©2023 Temenos Headquarters SA - all rights reserved.

Send Feedback